ALL EDITORS V401 — LOGIN PERSISTENCE + ACCOUNT-SPECIFIC NATIVE IMPORT

Use V401 for BG2:EE with an existing V399/V400 in-game account system.
V401 keeps V399 no-respawn behavior. Source files in ZIP are read-only.

1. CLOSE BaldurII.exe and run SETUP_IN_GAME_ACCOUNTS.bat.
2. IMPORTANT: Select the BG2 profile holding your actual Baldur.lua. If you
   changed engine.lua to use BaldursGate2Online, choose (for example):
   C:\Users\darks\Documents\BaldursGate2Online
   The installer offers that Documents profile automatically when it exists;
   otherwise use Browse. The game install remains unchanged.
3. Keep the original engine.lua backup yourself; setup does NOT touch engine.lua.

Account login: password authentication lasts for this BG2 process until exit;
menu -> multiplayer -> Arbitration transition does not request another login.
When the character router fails, you may Continue without reentering the
password; the character Import list remains denied if it cannot be verified.
A genuinely active account in another BG2 process is still protected.

Import: BG2's native CHARGEN_IMPORT list is filtered using the physical
<profile>/characters/*.CHR filenames. Only the authenticated account's exact
five-letter prefix plus TWO numeric digits are displayed and selectable
(e.g. Drakh01 or Krona01). Original Kronosya and Kronasya root filenames
are never authorized by those account prefixes. Filename ownership is
re-checked at Import opening, during display refresh, on selection and Done.
No external CHR text or internal displayed character name is trusted for access.

Export: stock BG2 Export panels are unchanged; BG2 writes its native CHRs into
<profile>/characters/. Folder-router code remains V400's V399-protected path;
this release adds a read-only physical inventory to its export snapshot.

No new shared-root router mode, no account migration, no bulk cleanup, no new
backup, no automatic file copying/restoration, and no engine.lua modifications.

TESTS: test_v401_login_and_root_import.py and V399 no-respawn checks cover
filename isolation, on-accept gating, menu login persistence, read-only scan,
and native Export panel preservation. Windows BG2 runtime testing required.

NOTE: Filtering is at the BG2 native Import UI level, not Windows file-system
ACLs. This is not a security barrier against a person with direct disk access.
